feat: improve changelog creation and auto label pr's#1146
feat: improve changelog creation and auto label pr's#1146Sim-sat wants to merge 2 commits intoCodeWithCJ:mainfrom
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a .github/release.yml configuration file to automate the generation of release notes. The review feedback suggests expanding the exclusion list to include non-user-facing labels such as refactor and backend, and adding specific categories for Security, Mobile, and Frontend to better organize the changelog output.
Sim-sat
force-pushed
the
improve-changelog
branch
from
f786b30 to
63ae43a
Compare
Sim-sat
force-pushed
the
improve-changelog
branch
from
63ae43a to
1a85eeb
Compare
Sim-sat
force-pushed
the
improve-changelog
branch
from
646c0e4 to
03bc5ce
Compare
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request updates the pull request template to include a mobile changes section and standardizes the linked issue format. It also introduces a configuration for automated release changelogs. Feedback points out that the PR description mentions automation workflows that are not included in the changes. Additionally, suggestions were made to add quality and translation checkboxes to the mobile section of the template and to exclude 'chore' and 'dependencies' labels from the release changelog.
|
Is this still in draft? |
It's working, I tested it on my fork, but I wanted to wait until you created the labels. I don't know what happens when they dont exist |
|
My bad. I didn't read the PR completely. Currently on mobile. I'm afraid I can do this only next weekend. |
|
Yeah don't worry it's not that important. Just tell me that when you add them
|
2 participants
Description
What problem does this PR solve?
What problem does this PR solve?
The current changelogs are difficult to read because they lack categorization and include technical debt or chores that provide no value to end-users.
How did you implement the solution?
I have improved the native GitHub release auto-generation by adding a release.yml configuration and a workflow that automatically labels PRs based on their titles and selected checkboxes. This automates organized changelogs without requiring manual intervention. I also improved the pr validation to make it a little bit less strict and to post a comment to make it easier to understand errors..
Suggested Label Updates
@CodeWithCJ I suggest creating the following labels to optimize categorization:
The mobile, frontend, and backend labels would only be used for making it easier for us to keep an overview, because github doesn't support nesting the categories in the changelog template.
Linked Issue: #
How to Test
...PR Type
Checklist
All PRs:
New features only:
Frontend changes (
SparkyFitnessFrontend/orsrc/):pnpm run validateand it passes.en) translation file.Backend changes (
SparkyFitnessServer/):rls_policies.sqlfor any new user-specific tables.UI changes (components, screens, pages):
Screenshots
Notes for Reviewers